-
-
Notifications
You must be signed in to change notification settings - Fork 680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enforce snake case in DM proc names. #11355
Enforce snake case in DM proc names. #11355
Conversation
Swapping to camelCase over snake_case is probably going to make TG ports harder ngl They aren't exactly clear on keeping a theme for procs versus typepath, but I figure I should put this here nonetheless |
Ah, typo in the PR name. Should read snake_case |
Script is almost functioning as intended now, just need to optimise it, fix some exceptional cases and then run it. I could do it a lot better, but it just needs to be a quick script that works once and never again. |
will we have an exception list? |
There's a phrase that will cause files to be skipped if it's found. This is applied to TGS, DBcore and ill exclude Initialize and Destroy |
Not sure how to do this in a way without destroying compatability with TG, will get back to this |
About The Pull Request
Enforce snake case in DM proc names, consistency and following a standard is good.
There are exceptions, capitalisation is allowed if the proc name is entirely capitalised, or if the section before or after an underscore is entirely capitalised. This means REF is valid, and get_REF is also valid.
TODO:
Why It's Good For The Game
Consistency is good, following proper code standards is good as it makes the code appear cleaner.
Testing Photographs and Procedure
See tests.
Renamed procs:
Changelog
🆑
code: Enforces camel case in DM proc names.
/:cl: